2015-03-04 - 16702 - Spec - Purchasing Controls #purchaserequisitions
SPECIFICATIONS
16702.200 - Spec - Purchasing Controls
Purpose
Purchasing Controls
Admin Info
| Purpose |
Purchasing Controls |
| Requested By |
Jeffrey Mau |
| Spec Created By |
Laxman |
| Spec Created Date |
03/04/2015 |
| Spec QA by |
Laxman |
| Objects |
BUS2105 |
| Document Status |
WIP |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
20 |
| 2 |
Documentation |
08 |
| 3 |
Development/ Config |
60 |
| 4 |
Unit test in DEV |
24 |
| 5 |
Unit test in QUA |
08 |
| 6 |
Other activity |
|
| TOTAL |
120 |
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
| 01 |
Even if the dollar limit is less than 50k the VP should be copied in cc |
Saravanan |
04/24/2015 |
|
| 02 |
VP also notified along with requester that PO has been issued |
Saravanan |
04/24/2015 |
|
| 03 |
Short text (description) also required in the notification along with requester, price and vendor |
Saravanan |
04/24/2015 |
|
| 04 |
Single approval if user is assigned to different positions of same Purch group |
Saravanan |
04/24/2015 |
|
| 05 |
Only requester is notified when the PR is converted to PO |
Jingsha |
05/04/2015 |
|
| 06 |
Need to forward the header text to approver in the email notification |
Jingsha |
05/07/2015 |
|
| 07 |
Notification should go to all the prior appoveres if rejected |
Jingsha |
05/30/2015 |
|
| 08 |
PO PDF to requester if MRO PR is converted to PO |
Jingsha |
05/30/2015 |
|
| 09 |
Create new purchasing group for MRO-Canada and setup release strategy |
Jingsha |
06/23/2015 |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]As per the business requirement these are changes required to the current workflow setup.
1. Tiered approval is required (instead of single approval) based on dollar limits.
2. Purchase requester needs a notification once the MRO PR is converted to PO.
3. Header text will forwarded to approver in the email notification to approve the purchase requisition. Header text will contain link. Then approver will open the document by click on the link.
4. Even if the dollar limit is less than 50K the VP should be copied in CC
5. Short text (description) also required in the notification along with requester, price and vendor
6. Single approval if user is assigned to different positions of the same Purch group.
7. Notification should go to all the prior approvers if PR is rejected.
8. PO PDF to requester if MRO PR is converted to PO.
9. Create new purchasing group for MRO-Canada and setup release strategy.
In Scope:
[List the activities to be included in scope]Out of Scope:
[Out of scope activities]Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Modify the current workflow setup as per the document given below by New Era
Automated Requesitioning Process (Hycner - February 12 2015) FINAL.pdf
1. Tiered approval is required (instead of single approval) based on dollar limits.
- Modify the current configuration from single approval to tiered approval as per the given document. If required need to modify the workflow setup also.
2. Purchase requester needs a notification once the MRO PR is converted to PO.
- To forward the email notification to requester when MRO PR is converted to PO setup a new email output. For this we need to modify the existing routine.
3. Header text will forwarded to approver in the email notification to approve the purchase requisition
- Need to enhance the sub type ZBUS2105
4. Even if the dollar limit is less than 50K the VP should be copied in CC
- Need to enhance the business object BUS 2105
5. Short text (description) also required in the notification along with requester, price and vendor
- Need to enhance the sub type ZBUS2105
6. Single approval if user is assigned to different positions of same Purch group.
- Modify the configuration accordingly
7. Notifications to all the prior approvers if PR is rejected.
8. PO PDF to requester when MRO PR is converted to PO.
9. Create new purchasing group for MRO-Canada and setup release strategy.
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| MM001 |
Create the MRO purchase requisition and execute the workflow |
Notifications for approval should go as per the document given by New Era |
| MM002 |
Convert MRO Purchase Req to purchase order |
Email notification will be triggered and forwarded to PR requester and VP |
| MM003 |
Create the MRO purchase requisition and attach any document. Then execute the workflow |
Attachment also should be forwarded to approver along with the notification |
Solution Details
[Provide complete technical details for configuration or programming here]
.As advised by New Era modify the current workflow setup
Issues
[List Issues / Bugs identified in configuration or development]